Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GR-51805] Verify init memory semantics #9687

Closed
wants to merge 25 commits into from

Conversation

graalvmbot
Copy link
Collaborator

This PR adds an explicit verification phase, InitMemoryVerificationPhase, that checks that all writes to init memory locations are "published" by a PublishWritesNode (also introduced by this PR, to replace FixedValueAnchorNode). This means all subsequent reads are connected to the PublishWritesNode instead of the original allocation node.

The javadoc for PublishWritesNode includes an explanation of init memory semantics.

@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label Sep 16, 2024
Benchmark has shown that this does not result in a measurable improvement in performance or memory usage. In the future we could try to a chieve a similar result by postponing lowering of CommitAllocationNodes.
@graalvmbot graalvmbot force-pushed the crefice/verify-killed-init branch from 1177b2d to 162e9bd Compare September 17, 2024 13:03
@graalvmbot graalvmbot closed this Sep 18, 2024
@graalvmbot graalvmbot deleted the crefice/verify-killed-init branch September 18, 2024 08:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OCA Verified All contributors have signed the Oracle Contributor Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants